A constrained subset of the blar archive format — for embedded systems, bootstrap environments, and any context where the full blar feature set (compression, encryption, codec expansion, signatures) is overkill.
mini_blar archives are valid blar archives: any blar implementation can read them. mini_blar's writer only emits a profile of the format, and its reader only handles that profile.
Built on BLIP.
mini_blar archives:
- May contain
FILEandDIRentries (TYPE=5, TYPE=7) - Use only
TYPE,CSUM,VALattributes (noCOMP,ENC,SEG,SIG) - Use only
xxhash64for content checksums - Have no compression, no encryption, no container expansion
If you need any of those, use blar.
./build # release (via nix build)
./build debug # debug (via zig build)
./test # run unit + CLI tests ┌──────────┐
│ BLIP │ varint + LP envelope + generic containers
└────┬─────┘
│
┌──────────────┴──────────────┐
▼ ▼
┌─────────────┐ ┌──────────────┐
│ mini_blar │ │ blar │
│ (this) │ │ (sister) │
└─────────────┘ └──────────────┘
constrained full feature set
FILE/DIR only + codecs, comp, enc
xxhash64 only + GUI, signatures
mini_blar and blar are sister projects. mini_blar does not depend on blar. Both depend on BLIP. The two impls share a wire-format profile, not code.
See LICENSE.